Comments (4)
While the proper solution would be to fix both issues (by using the filesystem as the temporary storage for archives while they're created and by uploading logs to S3 in parallel), I think there is a quicker approach that could postpone both problems.
Right now we're handling and uploading the logs for all the crates, even the ones that were not regressions. Because of that, most of the logs we upload are actually useless (like the logs for test-pass
crates). If we were to change the report process to just avoid processing uninteresting logs we would save storage space and make the problems go away for a long time.
from crater.
I think we should move the tarballs to disk, but I at least find it sometimes helpful to look for past successful crate builds. I wouldn't stop uploading them personally; I think the reliability issues here should be solved by moving to disk storage for the tarballs.
from crater.
Honestly I thought test-pass + test-pass
results were never looked at. If someone actually uses them it's fine to keep them!
from crater.
#659 takes a start at this, by only uploading regressed crate's logs as raw files (vs. compressed tarballs). Should drastically speed things up for most crater runs.
from crater.
Related Issues (20)
- Have a separate category in the report for crates using nightly features
- The SQLite database is hard to manage in production HOT 1
- Proactively delete old Docker images and dangling containers
- runner going down with scheduled work stalls experiment HOT 1
- "Temporary failure in name resolution" is a popular source of spurious failures
- Latest commit (9503083) compiles forever, eventually OOMs HOT 2
- Triaging/improving the number of crates classified as build-fail HOT 1
- Completion percentage can be over 100%
- Tons of spurious failures due to build scripts failing to run rustc HOT 11
- Automatic verification of potential regressions
- Should `tokio` really be marked as broken?
- Disk full errors should be spurious HOT 6
- Automatic detection of spurious regressions
- Numbers in final reports are confusing
- test timout to compiler error marked as spurious
- "root results" does not list the biggest root regression HOT 2
- Limit available parallelism to 1 per 2GB of RAM HOT 1
- Crater seems to sometimes test outdated crates HOT 3
- Crater log of "current run" always begins with "previous run"
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from crater.