Github user liuyuzhong commented on the issue:
https://github.com/apache/flink/pull/2439
Jenkins run error:
```
Running
org.apache.flink.test.checkpointing.PartitionedStateCheckpointingITCase
SUREFIRE-859: Java HotSpot(TM) 64-Bit Server VM warning: INFO:
os::commit_memory(0x00000000d8b00000, 100663296, 0) failed; error='Cannot
allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 100663296 bytes for
committing reserved memory.
# An error report file with more information is saved as:
#
/home/jenkins/jenkins-slave/workspace/flink-github-ci/flink-tests/target/hs_err_pid9818.log
Running org.apache.flink.test.checkpointing.WindowCheckpointingITCase
ERROR: Maven JVM terminated unexpectedly with exit code 137
Putting comment on the pull request
Finished: FAILURE
```
But I run it successfully in my environment, does it a Jenkins memory
problem? Rerun it in Jenkins?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
