# Deprecation Warnings Not Showing

**URL:** <https://discourse.julialang.org/t/deprecation-warnings-not-showing/11171>\
**Category:** General Usage\
**Created:** [May 26, 2018, 9:57pm UTC](https://discourse.julialang.org/t/deprecation-warnings-not-showing/11171 "2018-05-26T21:57:47Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![JaredCrean2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jaredcrean2/32/3574_2.png) [@JaredCrean2](https://discourse.julialang.org/u/JaredCrean2)\
**Post date:** [May 26, 2018, 9:57pm UTC](https://discourse.julialang.org/t/deprecation-warnings-not-showing/11171/1 "2018-05-26T21:57:47Z")

</div>

I am upgrading a package to Julia 0.6.2, and I noticed deprecation warnings in the Travis logs that are not present when I run the tests locally.

The output from the local run (both stdout and errout) is [here](https://gist.github.com/JaredCrean2/250af4f4505067d65109213549f12745), and the output from the Travis log is [here](https://travis-ci.org/OptimalDesignLab/ODLCommonTools.jl). The deprecation warning on line 480 of the Travis log does not appear in the output for the local run.

The output from `versioninfo()’ is

```julia
Julia Version 0.6.2
Commit d386e40* (2017-12-13 18:08 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
  WORD_SIZE: 64
  BLAS: libopenblas (USE64BITINT DYNAMIC_ARCH NO_AFFINITY Prescott)
  LAPACK: libopenblas64_
  LIBM: libopenlibm
  LLVM: libLLVM-3.9.1 (ORCJIT, broadwell)

```

and shows the versions of Julia on Travis and my local machine are exactly the same. I’m rather stumped as to what would cause this. The package can be found [here](https://github.com/OptimalDesignLab/ODLCommonTools.jl/tree/upgrade_0.6), using the `upgrade_0.6` branch.

---

<div class="post-metadata">

**Author:** ![Elrod](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/elrod/32/22461_2.png) [@Elrod](https://discourse.julialang.org/u/Elrod)\
**Post date:** [May 27, 2018, 12:00am UTC](https://discourse.julialang.org/t/deprecation-warnings-not-showing/11171/2 "2018-05-27T00:00:37Z")

</div>

A lot of warnings only come up while precompiling a module. Perhaps that’s the issue?

Although if you’re making changes, it should be recompiling, so you ought to see deprecation warnings for using `type` instead of `mutable struct` when `using ODLCommonTools` for the first time after making changes, as an example: [https://github.com/OptimalDesignLab/ODLCommonTools.jl/blob/f3e15b6a724c71a7bc336462a3054c02c6fdd924/src/types.jl](https://github.com/OptimalDesignLab/ODLCommonTools.jl/blob/f3e15b6a724c71a7bc336462a3054c02c6fdd924/src/types.jl)

---

<div class="post-metadata">

**Author:** ![JaredCrean2](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jaredcrean2/32/3574_2.png) [@JaredCrean2](https://discourse.julialang.org/u/JaredCrean2)\
**Post date:** [May 27, 2018, 12:13am UTC](https://discourse.julialang.org/t/deprecation-warnings-not-showing/11171/3 "2018-05-27T00:13:20Z")

</div>

You’re right, deleting the .ji files caused the the deprecation warnings to be printed the when the module was precompiled again.

Thanks for the quick response,  
Jared Crean