Aphek
90a64f5201
Fix monthly notifications
2025-12-26 13:23:55 +01:00
d15a746558
make it blazingly fast with caching of css and js
2025-11-28 23:54:43 +01:00
f539a3c45c
migrate to rootcause
2025-11-28 23:28:19 +01:00
25179d488d
remove wrong text
2025-11-22 13:39:45 +01:00
e523607cbc
Improve design
...
Highlight that there are build details available with a `[details]`
link which wasn't obvious before.
2025-11-14 22:16:32 +01:00
5b62eaff57
Add more information
2025-11-14 22:01:29 +01:00
Jens Reidel
9c71be05a8
Sign me up for some target notifications
...
Signed-off-by: Jens Reidel <adrian@travitia.xyz>
2025-11-14 21:43:12 +01:00
45f784eb5c
Improve margin on mobile
2025-11-11 19:35:03 +01:00
310a24aa44
Make it look much better
...
Including dark mode!
2025-11-11 19:26:28 +01:00
1d31b9c3fe
Cleanup
2025-11-11 19:04:14 +01:00
73098095a7
Optimize features
2025-11-11 19:03:37 +01:00
491eb1604f
Only send notification update after a month of inactivity
...
A lower cadence was requested in https://github.com/Noratrieb/does-it-build/pull/10#issuecomment-3514228933
2025-11-11 18:47:25 +01:00
b244cf05b4
Update README.md
2025-11-10 23:24:41 +01:00
91f043de7d
Add License ( #11 )
...
All contributions from other contributors have been too small too have any meaningful copyright, so I'll just do this. Useful for the future.
2025-11-10 23:22:46 +01:00
e4c69f17be
Add notifications for target maintainers ( #10 )
...
This adds a feature where maintainers can add themselves to an array in the source to receive notifications whenever the target fails.
The way this works is via GitHub, I created a new repository https://github.com/Noratrieb/does-it-build-notifications where an app will create issues that ping the respective users. This is the easiest option for me and also fits nicely into people's workflows on GitHub.
Whenever a target fails, an issue is created for it. This issue is kept open (with a new comment every day that it continues to fail), and then closed when the target builds again.
2025-11-10 20:52:15 +01:00
112420d224
update
2025-11-01 14:44:26 +01:00
6bff95d9bb
Cleanup parameter type
2025-10-05 12:05:47 +02:00
0f749df239
Update dependencies
2025-10-05 12:05:07 +02:00
Cherry
b213eec65d
Fix typos
2025-09-12 20:48:16 +02:00
8179082517
delete core stuff
2025-07-12 13:29:17 +02:00
c90b94ee69
Handle pre-2024 cargo and pre-knows-whether-to-build-std cargo
2025-07-12 13:29:17 +02:00
9f18ad0d06
-j1
2025-07-12 13:29:17 +02:00
8e9ff1e9fd
Run cargo build instead of cargo check for std
...
And use --release and respect rustflags.
Just to make doubly-sure that even in the future, a build will be done
instead of check.
2025-07-12 13:29:17 +02:00
4969eaeb36
Stop building core
...
Core is now a subset of std
2025-07-12 13:29:17 +02:00
df486c20f8
Use cargo check -Zbuild-std instead of cargo miri setup
...
This should be more reliable (not building with `cfg(miri)` and more
accurately knowing whether a target supports std).
Known targets affected by this change:
- cygwin: should now build since it only breaks in `cfg(miri)`
- i686-pc-nto-qnx700: officially doesn't support std
closes #4
2025-07-05 14:21:26 +02:00
0be7b4c981
remove console.log
2025-07-05 10:53:45 +02:00
5fb3ca86b2
Support suspending background thread
...
Useful for locally testing query timings with sqlx debug logging.
2025-07-04 23:09:52 +02:00
6df7155a50
Add index for build stats
...
Otherwise it's very slow :)
2025-07-04 23:04:51 +02:00
7f1702bc28
Store more metadata
...
And other various improvements
2025-07-04 22:47:06 +02:00
f6fac25c6f
Remove old link and show number of builds
...
In the users locale of course. Without any annoying Accept-Language
parsing or anything like that, just with the beauty of JavaScript.
2025-07-04 22:06:40 +02:00
3f302c7180
Fix failure filtering for std
...
std failures weren't getting filtered properly since I only checked
core.
2025-07-04 18:48:16 +02:00
9de21d4198
Say the build has no changes for DOES_IT_BUILD_OVERRIDE_VERSION
2025-07-04 18:43:29 +02:00
b1d1728c42
Support using custom rustflags for targets
...
This is necessary for AVR and AMDGPU. We currently just hardcode some
flags in the binary, which is good enough. There's a new column which
keeps track of the used flags and shows them for a build.
A migration makes sure that the older results are properly backfilled
with the flags to make them build.
2025-07-04 18:23:00 +02:00
42cd9fda83
Add filtering for failures
2025-07-04 17:55:22 +02:00
abb83f24b2
don't go that far back
2025-07-04 17:41:47 +02:00
3d16b9d460
Be more clear about build kind
2025-07-04 17:38:48 +02:00
Pietro Albini
032e023b25
Stop guessing nightlies not included in manifests.txt ( #3 )
...
The file is now automatically updated after every release!
2025-07-04 17:34:41 +02:00
5ec24bbfaf
Surface broken nightly errors
2025-07-03 22:20:00 +02:00
cfef23bc31
build even older nightlies
2025-07-03 21:52:44 +02:00
79bb6d1eb0
Cleanup and perf
2025-07-03 19:44:03 +02:00
61d78680e0
Add nightly overview pages
2025-07-03 19:26:02 +02:00
7f4c69e51f
Make it more robust
2025-06-29 23:51:06 +02:00
cc4d90e748
rewrite frontend to be less fucked
2025-02-05 22:00:00 +01:00
Joe ST
3012189906
improve filter fields
...
adding ` type="search"` to the filter fields causes browsers to add a little x to the field to 'cancel' the search and clear the field
2024-09-08 20:48:54 +02:00
e639507a42
clarify build
2024-09-08 16:56:32 +02:00
67459f825b
Improve table
2024-09-08 15:34:12 +02:00
ae1f0b96e3
hacky way to configure parallelism
2024-09-08 12:31:28 +02:00
5ef63686f3
Guard against completely broken nightlies
2024-09-08 12:25:36 +02:00
4671f871a6
Add support for more recent nightlies than the manifest supports
2024-09-08 12:18:30 +02:00
262e8acd9f
add miri std support
2024-09-08 11:44:43 +02:00
