Skip to content

Fix Time#localtime(0) being treated as UTC. #7

Fix Time#localtime(0) being treated as UTC.

Fix Time#localtime(0) being treated as UTC. #7

Triggered via push September 16, 2025 19:27
Status Failure
Total duration 6h 2m 37s
Artifacts

ci.yml

on: push
Matrix: mvn-test-extended
Matrix: mvn-test
Matrix: rake-test-indy-off
Matrix: rake-test
jruby-tests-dev
2m 38s
jruby-tests-dev
regression-specs-jit
2m 36s
regression-specs-jit
mvn -Ptest, rake test:jruby (Windows, Java 21)
9m 40s
mvn -Ptest, rake test:jruby (Windows, Java 21)
Dependency check
1m 40s
Dependency check
Verify build artifacts
3m 41s
Verify build artifacts
sequel
6h 0m
sequel
concurrent-ruby
6m 23s
concurrent-ruby
run specs repeatedly to test optimizations
11m 17s
run specs repeatedly to test optimizations
mvn -Ptest (OpenJ9 Java 21)
7m 17s
mvn -Ptest (OpenJ9 Java 21)
shellcheck jruby.sh
10s
shellcheck jruby.sh
Matrix: rake-test-multiplatform
publish-snapshot  /  publish
publish-snapshot / publish
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 1 notice
rake spec:ruby:fast (Java 23)
Process completed with exit code 1.
rake spec:ruby:fast (Java 21)
Process completed with exit code 1.
rake spec:ruby:fast:jit (Java 23 -indy)
Process completed with exit code 1.
rake spec:ruby:fast:jit (Java 21 -indy)
Process completed with exit code 1.
rake spec:ruby:fast:jit (Java 23)
Process completed with exit code 1.
rake spec:ruby:fast:jit (Java 21)
Process completed with exit code 1.
sequel
The operation was canceled.
sequel
The job has exceeded the maximum execution time of 6h0m0s
mvn -Ptest, rake test:jruby (Windows, Java 21)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677